Adaptive spectrum as a service

ABSTRACT

The described technology is generally directed towards adaptive spectrum as a service, in which spectrum can be dynamically allocated to adapt to demand for wireless capacity. The demand for wireless capacity can be based on monitoring system state, and/or proactively predicted based on other system state such as time of day. Reallocated spectrum can be monitored for performance, to converge spectrum allocation to a more optimal state. Allocated spectrum can be relocated, increased or decreased, including by the use of citizens band radio service spectrum or other spectrum. Currently allocated spectrum can be adapted into modified allocated spectrum by an application program (xApp) coupled to a radio access network intelligent controller (RIC), a citizens broadband radio service device, a domain proxy service, and/or a user device. A user device can determine and request bandwidth, with spectrum allocated in response.

BACKGROUND

Spectrum used in wireless communications is a valuable and limitedresource. Spectrum in the United States is managed by the FederalCommunications Commission (FCC), which distinguishes between licensed,unlicensed and shared spectrum. The FCC controls and manages someportions of the spectrum as unlicensed spectrum to end customers such asprivate enterprises. Other portions of the spectrum are designated forunlicensed users, while other parts can be shared.

One example of shared spectrum is Citizens Broadband Radio Service(CBRS), which refers to the 150 megahertz (MHz) portion of the spectrumfrom 3550 MHz to 3700 MHz. A spectrum access system (SAS) manages CBRSspectrum sharing to avoid interference among incumbent access users(e.g., government and satellite users) who have the highest priority,priority access users (e.g., enterprises that have purchased a license)who have the next-highest priority, and general authorized access userswho have the lowest priority.

Previously, private companies were required to get exclusive licensedspectrum from network operators, which is a manual process, takes muchtime and is not automated at all. As the use of wireless communicationscontinue to grow globally, wireless spectrum allocation is a significanttopic. The amount of available spectrum is relatively very small, andinterference can be problematic.

BRIEF DESCRIPTION OF THE DRAWINGS

The technology described herein is illustrated by way of example and notlimited in the accompanying figures in which like reference numeralsindicate similar elements and in which:

FIG. 1 is a block diagram representation of example components andinterfaces of a communications network configured to adapt allocated, inaccordance with various aspects and implementations of the subjectdisclosure.

FIG. 2 is an example block diagram representation of allocating andreallocating spectrum over time, including changing a downlink to uplinkratio, in accordance with various aspects and implementations of thesubject disclosure.

FIG. 3 is an example block diagram representation of telemetry datagathering, analytics of telemetry data and actions to adapt spectrum, inaccordance with various aspects and implementations of the subjectdisclosure.

FIG. 4 is a block diagram representation of example components includinga radio access network intelligent controller (RIC) and an applicationprogram (xApp) integrated into a wireless communications network tofacilitate adapting spectrum based on various information, in accordancewith various aspects and implementations of the subject disclosure.

FIGS. 5 and 6 comprise a dataflow and timing representation showingexample communications between components (e.g., of FIG. 4 ) to allocatecitizens band radio service (CBRS) spectrum on demand, in accordancewith various aspects and implementations of the subject disclosure.

FIG. 7 is a block diagram representation of example components includingan eNodeB/gNodeB (eNB/gNB) configured to adapt spectrum based on variousinformation, in accordance with various aspects and implementations ofthe subject disclosure.

FIGS. 8 and 9 comprise a dataflow and timing representation showingexample communications between components (e.g., of FIG. 7 ) to allocatecitizens band radio service (CBRS) spectrum on demand, in accordancewith various aspects and implementations of the subject disclosure.

FIG. 10 is a block diagram representation of example componentsincluding a domain proxy configured to adapt spectrum based on variousinformation, in accordance with various aspects and implementations ofthe subject disclosure.

FIGS. 11 and 12 comprise a dataflow and timing representation showingexample communications between components (e.g., of FIG. 10 ) toallocate citizens band radio service (CBRS) spectrum on demand, inaccordance with various aspects and implementations of the subjectdisclosure.

FIG. 13 is a block diagram representation of example componentsincluding a user device configured to request an adapting of spectrum toincrease or decrease bandwidth based on various information, inaccordance with various aspects and implementations of the subjectdisclosure.

FIGS. 14 and 15 comprise a dataflow and timing representation showingexample communications between components (e.g., of FIG. 13 ) toallocate citizens band radio service (CBRS) spectrum on demand, inaccordance with various aspects and implementations of the subjectdisclosure.

FIG. 16A depicts an example cell of a wireless communications network inwhich additional spectrum is added to the cell and a hotspot isrelocated within the cell, in accordance with various aspects andimplementations of the subject disclosure.

FIG. 16B depicts example group of cell of a wireless communicationsnetwork in which spectrum is modified in two of the cells and a hotspotis relocated from one cell to another cell, in accordance with variousaspects and implementations of the subject disclosure.

FIG. 17 is a flow diagram representing example operations related to auser device determining and signaling for bandwidth data, in accordancewith various aspects and embodiments of the subject disclosure.

FIG. 18 is a flow diagram representing example operations related to auser device communicating with a network device to request and receiveadditional bandwidth, in accordance with various aspects and embodimentsof the subject disclosure.

FIG. 19 is a flow diagram representing example operations related to auser device determining additional bandwidth and receiving correspondingscheduling data, in accordance with various aspects and embodiments ofthe subject disclosure.

FIG. 20 illustrates an example block diagram of an example mobilehandset operable to engage in a system architecture that facilitateswireless communications according to one or more embodiments describedherein.

FIG. 21 illustrates an example block diagram of an examplecomputer/machine system operable to engage in a system architecture thatfacilitates wireless communications according to one or more embodimentsdescribed herein.

DETAILED DESCRIPTION

Various aspects of the technology described herein are generallydirected towards dynamically allocating spectrum to seamlessly adapt(e.g., scale up or down) wireless capacity based on user demand. Thedemand can be actual demand determined from various metrics,anticipated/expected demand predicted based on historical data and/orexternal information, or a combination of actual demand andanticipated/expected demand. Spectrum allocation can be performed withina coverage area and/or for a limited time, and can be deployed with aconfiguration that is relatively efficient for a usage scenario at thatlocation and/or time. For example, the technology facilitates flexibleadjustment of the uplink-to-downlink ratio in a coverage area.

By way of example, consider the citizens broadband radio service (CBRS).At times of high demand in which more wireless network wireless capacityis needed to service users, the technology described herein operates torequest a grant of some portion of CBRS spectrum. When granted, thetechnology makes the granted portion of the CBRS spectrum available forscheduling uplink and downlink transmissions of user equipment. Inanother example, a hotspot can be relocated (e.g., a mobile hotspot canbe moved, or a hotspot a one location can be deactivated and anotheractivated at a different location) to adapt to current demand forwireless communications wireless capacity.

It should be understood that any of the examples herein arenon-limiting. For instance, some of the examples are based on CBRS,however the technology described herein is applicable to cellularcommunication frequencies as well as Wi-Fi and other wirelesstechnologies (Bluetooth®, satellite). Whereas the FCC regulates the CBRSspectrum through SASs, the concepts presented herein may be similarlyapplicable to operator-provided spectrum that can be brokered or managedas-a-Service, similarly to CBRS. As described herein, spectrum istreated as a resource that can be requested seamlessly, adaptively andon-demand as Spectrum-as-a-Service. Thus, any of the embodiments,aspects, concepts, structures, functionalities or examples describedherein are non-limiting, and the technology may be used in various waysthat provide benefits and advantages in communications and computing ingeneral.

It also should be noted that terms used herein, such as “optimize,”“optimization,” “optimal” and the like only represent objectives to movetowards a more optimal state, rather than necessarily obtaining idealresults. For example, “optimizing” a network/system/cell means movingtowards a more optimal state, rather than necessarily achieving anoptimal result. Similarly, “maximize”, such as to “maximize throughput”means moving towards a maximal state, not necessarily achieving such astate.

Reference throughout this specification to “one embodiment,” “anembodiment,” “one implementation,” “an implementation,” etc. means thata particular feature, structure, or characteristic described inconnection with the embodiment/implementation can be included in atleast one embodiment/implementation. Thus, the appearances of such aphrase “in one embodiment,” “in an implementation,” etc. in variousplaces throughout this specification are not necessarily all referringto the same embodiment/implementation. Furthermore, the particularfeatures, structures, or characteristics may be combined in any suitablemanner in one or more embodiments/implementations.

Aspects of the subject disclosure will now be described more fullyhereinafter with reference to the accompanying drawings in which examplecomponents, graphs and/or operations are shown. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding of the variousembodiments. However, the subject disclosure may be embodied in manydifferent forms and should not be construed as limited to the examplesset forth herein.

FIG. 1 shows example system architecture 100 of various elements andinterfaces, including elements involved in spectrum management. Notethat the example system architecture 100 of FIG. 1 is capable of usingCBRS spectrum via citizens broadband radio service devices (CBSDs) 102and 104, however it is understood that this is a non-limiting example.Dynamic spectrum allocation technology as described herein can beimplemented based on any available spectrum.

In the example of FIG. 1 , a user equipment (UE) device 106 connects toother elements of the system 100 via the eNodeB (eNB) or gNodeB (gNB),which as exemplified in FIG. 1 are incorporated into a device 102 thatsupports citizens broadband radio service, as a CBSD. Communications canbe based on conventional fourth generation long term evolution (LTE)technology and new radio (NR) technology such as fifth generation (5G)and beyond. The exemplified UE device 106 is configured to communicateover the CBRS spectrum, if the device 102 schedules the device 106 to doso, or can be scheduled to use LTE and/or new radio cellularfrequencies. Note that in an implementation in which CBRS spectrum isdynamically allocated in a coverage area, as long as one or more userdevices can operate in the CBRS spectrum, benefits of dynamic allocationvia CBRS such as increased wireless capacity can be realized in thatcoverage area regardless if other active user devices in the area do notsupport CBRS communications.

Once connected to the system, the user device 106 communicates via thenetwork device 102, that is, the eNodeB (eNB) for LTE or gNodeB (gNB)for standalone new radio, or eNB and gNB both for non-standalone newradio and/or in a dual connectivity mode. The eNB and/or gNB are coupled(e.g., via an S5 or N3 interface, respectively) to a core network 108(the evolved packet core (EPC) network 108 or 5G core network,respectively). In turn, the core network 108 is coupled (via a packetgateway and the sGI interface for EPC or user plane function and the N6interface for 5GC) to an external internet protocol (IP) domain,exemplified in FIG. 1 as IP network 110.

In general, to operate in the CBRS spectrum, the eNB/gNB 102 couples toa spectrum access system 112 through a domain proxy 114 via a SAS-CBSDinterface. The domain proxy 114 facilitates the coupling of multipleeNBs/gNBs to couple to the spectrum access system 112, rather than havea group of individual eNBs/gNBs more directly communicate with thespectrum access system 112.

The spectrum access system (SAS) 112 via the domain proxy 114 andapplication programming interface (API) set allows a CBSD (e.g., device102) to register to receive a unique identifier from the SAS 112. Onceregistered, the CBSD can deregister from the SAS, such as if the CBSD isdecommissioned or moved.

When registered, the CBSD can inquire (via a CBSD basic spectruminquiry) to determine what spectrum is available given the CBSD'slocation and installation characteristics. Assuming some spectrum isavailable, the SAS 112 grants requests when a CBSD requests a grant of aportion of the CBRS spectrum for use.

Note that once the reservation has been made and a grant request isapproved, the CBSD is not yet authorized to transmit using the grant.Instead, the CBSD periodically sends a heartbeat request for eachapproved grant, which, if transmission is allowed, returns authorizationto transmit. The CBSD relinquishes a grant when no longer needed foruse.

In FIG. 1 , a radio access network (RAN) intelligent controller (RIC116), in conjunction with an application program (referred to as an xApp118) provides for one way in which dynamic spectrum allocation isadaptable for a wireless communication usage scenario. When configured,the xApp 118 can communicate with the SAS 112 (e.g., via an interface1a) and the domain proxy 114 (e.g., via an interface 1a). The device 102communicates with the RIC 114 via O-RAN (Open RAN) interfaces, includingthe E2/A1/O1 interfaces. Other ways described herein include extending aCBSD's capabilities, extending a domain proxy's capabilities, and/orextending a UE device's capabilities.

As shown in FIG. 1 , via various interfaces J1-J4, a global multisitecontroller 120 can communicate with the UE device 106, xApp 118, domainproxy 114, and eNB/gNB device 102. Among its functions, the globalmultisite controller 120 can return metadata related to dynamic spectrumallocation, including thresholds (e.g., that when met trigger dynamicspectrum allocation and reallocation), incremental claim steps (how muchat a time that claimed dynamic spectrum allocation is to increase ordecrease) and an observation time window (e.g., the last x seconds,minutes, hours, days, weeks or month(s) of monitored data for thepurpose of evaluating the thresholds). The global multisite controller120 can perform inventory updates, telemetry setup, analyze adjacentcells and their configurations, and prepare an initial configuration.The global multisite controller 120 also can perform analytics (e.g.,via machine learning (ML), artificial intelligence (AI) and/or rules),can develop a spectrum adjustment plan, and verify the spectrumadjustment plan verification through the SAS 112.

FIG. 2 shows a general conceptual example of dynamically allocatingspectrum. In a first time period, 10 MHz of spectrum is available forscheduling wireless network communications to and from (downlink anduplink) UE devices in a served coverage area. At time period t2,increased demand for wireless capacity is detected (or predicted),resulting in dynamic allocation of additional spectrum to adapt to theincreased demand, which in the example of FIG. 2 is an additional 100MHz plus 20 MHz. For example, in a CBRS environment (where at most 150MHz can be granted), additional spectrum can be requested from aspectrum access system (SAS), and if granted and transmission is allowed(e.g., for the time period t2), the additional spectrum can be allocatedfor use in scheduling downlink and uplink communications. In otherscenarios, additional spectrum can be leased or moved from one locationto another within the coverage area and/or moved from an adjacentcoverage area (which would otherwise be unavailable because ofinterference with the adjacent coverage area).

In a third time period t3, less wireless capacity is needed, and thusthe amount of useable spectrum is reduced. This can be by moving aportion of the total spectrum to another location, or by relinquishingat least some CBRS spectrum or other spectrum. Note that the timeperiods t1-t3 are shown in FIG. 2 as generally the same in length,however this is a non-limiting example, and equal as well as unequaltime periods may be present in a given usage scenario.

FIG. 2 also illustrates how the uplink-to-downlink (UL:DL) ratio can beconfigured for at least some of the spectrum. Note that the CBRS is atime-division-duplex band and thus adjusting the UL:DL ratio isstraightforward via different frame structure configurations. Duringtime period t2, the uplink-to-downlink (UL:DL) ratio is n:n (e.g. 4:4)within the additional 100 MHz range. During time period t3, theuplink-to-downlink (UL:DL) ratio is n:m (e.g. 2:6) within the additional30 MHz range (as reduced from the previous time period t2's 100 MHzrange).

Dynamic spectrum allocation can thus be used in any coveragearea/timeframe to adapt to demand for wireless capacity, as well asdeployed with a configuration that is efficient for the usage scenariogiven a certain time. Some non-limiting example use cases that canbenefit through dynamic spectrum allocation as described herein includea shopping mall, in which additional spectrum can be made available neara food court during lunch hours, as opposed to other shopping hours inwhich the spectrum can be more equally distributed throughout the mall.Another example can be a large distributed-location factory, withchanging wireless activities across the factory facilities depending onthe time and location of ongoing work. Equal and static wirelesscapacity distribution is unlikely, and thus the locations/facilities canbe provisioned with spectrum as needed. In another example, consider anin-house distributed antenna system that is deployed for use in officespace on the ground floor(s) and housing above, where more spectrum maybe needed in the office during working hours, and more spectrum neededin the housing area at other times. An airport (or other similarfacility such as a commuter train station) can balance spectrum acrossterminals depending on schedules, e.g., passenger amounts due todeparting or arriving flights at the airport can be known in advance toprovision and re-provision spectrum as needed. Thus, actual demand,predicted demand and/or external data such as commuting schedules can beused to dynamically adapt spectrum allocation to a usage scenario.

Moreover, the uplink-to-downlink ratio can be configured as shown inFIG. 2 . As another non-limiting example, a concert venue, pressconference, speech or the like provides a usage scenario in whichattendees tend to upload live or nearly live videos to social media orthe like, and thus scheduling for more uplink communications thandownlink communications may be appropriate during such an event. Incontrast, a televised sporting event may have many event attendeesdownloading a live-streamed video of the event, such as to see replays,zoomed-in camera views, different camera angles and so forth, wherebyscheduling to facilitate more downlink communications than uplinkcommunications may be appropriate during the event.

FIG. 3 shows a conceptual example of adapting spectrum to modify thesystem state, such as for a coverage area (which can be an area within asingle cell, multiple cells, or an entire network). Telemetry data,logging data and monitoring data 330 are obtained and fed into ananalytics, predictions and rules engine 332 or the like. Telemetry datacan be gathered throughout the end-to-end system including connectiontype, subscriber information, location, context, connection importanceand cost per bit. These and other factors can be considered as inputparameters for an adaptation algorithm. Based on the various data 330,the analytics, predictions and rules engine 332 can change the currentsystem state 334, e.g., by an action 336 (or multiple actions) thatincreases or decreases allocated spectrum and/or changes theuplink-to-downlink ratio. Note that the system state can include time ofday, day of week, a planned event, a schedule (e.g., commuter orpassenger schedules) and so forth, such that spectrum can be proactivelyadapted, instead of or in addition to reactive adaptation of spectrumbased on measured conditions and the like. The changed state is inputinto a reward function 338, which in conjunction with updated (followingthe changed state) telemetry data, logging data and/or monitoring data330, is processed by the (real-time and non-real-time) analytics,predictions and rules engine 332 to move the overall system to a moreoptimal state.

In this way, a system can thus converge towards a generally optimalsystem state over time. Note however that even when converged such astate is not necessarily static, and various factors such astime-of-day, the start or end of a largely attended event and so on canrevise the system state in a relatively fast (coarse) manner as opposedto a gradual fine-tuned convergence.

Returning to FIG. 1 , as set forth herein, the metadata from the globalmultisite controller 120 can include incremental and other change datacorresponding to changing currently claimed spectrum data, thresholddata or an observation time window. The incremental data can include afirst step size, indicating an amount of allocated spectrum to increasein a spectrum addition operation, and a second step size, indicating anamount of allocated spectrum to decrease in a spectrum reductionoperation. The step size to increase or decrease can be the same. Forexample, the incremental data can specify adding to/removing useablespectrum from a sector or cell step sizes per increment, such as 5 MHz,10 MHz, 20 MHz, 40 MHz, and so forth. Other change metadata can specifythat the system enable/disable one or more radio technologies (e.g., 4G,5G, 6G, Wi-Fi 802.11n, 802.11ac, 802.11ax, etc.). It is feasible to forthe metadata to indicate a different rate of change, such as viadifferent observation time windows depending on whether the previousspectrum adaptation was to increase or reduce the allocated spectrum.

The threshold data can include values representing a maximum wirelesscapacity for a channel (where a channel can be any portion of allocatedspectrum as defined by the system), a peak wireless capacity for thechannel, available wireless capacity data, current wireless capacityused data, a maximum number of supported active users in a cell, amaximum number of supported active users in a radio access network, amaximum number of supported active users in a core, a current number ofactive users in the cell, a current number of active users in the radioaccess network, and/or a current number of active users in the core.Further threshold data can include a current number of idle users in thecell, a current number of idle users in the radio access network, acurrent number of idle users in the core, estimated available wirelesscapacity for additional users in the cell, estimated available wirelesscapacity for additional users in the radio access network, and/orestimated available wireless capacity for additional users in the core.The thresholds can correspond to traffic heuristics based on time,traffic heuristics for the cell, traffic heuristics for a location inthe cell, and/or traffic heuristics based on an event. Any of thethreshold values can be monitored against actual current condition(s),and if a threshold value is violated, an action corresponding to anincremental step or other change can be taken to adapt the allocatedspectrum to the condition(s).

After at least one incremental step/change that adapts the currentlyallocated spectrum into the allocated spectrum, various performance datacan be monitored to evaluate the result (successfully improved theperformance or performance worsened) of the change. Such performancedata (e.g., for before and after comparison and/or comparison versusthreshold data) can include dropped call data, dropped session data,active user data, idle user data, throughput data per device, cellthroughput data, radio access network throughput data, core-networkgateway throughput data, interference data that measures interferencebetween cells, and/or interference data that measures interferencebetween sectors

As set forth herein, one way to implement the spectrum adaptingtechnology as described herein is to leverage an xApp and RANIntelligent Controller (RIC). Such an implementation facilitatesadaptive dynamic spectrum allocation over multiple eNBs/gNBs, which mayinclude an area, a region, or any group of cells up to a completecellular carrier's network.

As shown in the example system 400 of FIG. 4 , which is based on OpenRAN, or O-RAN, a radio unit (e.g., new radio, 5G or beyond) is coupled(F2 interface) to a (virtualized) distributed unit 440 (a logical nodeof the gNB), which in turn couples to a centralized unit, divided into acentralized unit control plane 442 (a logical node of the gNB) and acentralized unit user plane 442 (a logical node of the gNB). Thecentralized units 442 and 444 couple to the core, with the centralizedunit control plane 442 coupling to a core control plane 446 via an N2interface, and the centralized unit user plane 444 coupling to a coreuser plane 446 via an N3 interface.

As further shown in FIG. 4 , a RIC 416 has integratedmonitoring/telemetry capabilities (represented in FIG. 4 asmonitoring/telemetry data collector 450), and as is known, gatherssystem utilization data via O-RAN-defined E2/A1/O1 interfaces. Forexample, the RIC can obtain optional core network telemetry from thecore/other components via the E2 interface.

As is known, a RIC is divided into a non-real time logical function(e.g., in service management and orchestration) and a near-real timelogical function that couples to xApps, including the xApp 418 asdescribed herein. In general, functions hosted by xApps allow servicesto be executed at the near-real time RIC 416, with actions sent to thegNB distributed unit and centralized unit nodes via the E2 interface.The combination of data (e.g., monitoring data, performance data and soforth) obtained from the non-real time logical function (via the A1interface) and any (optional) core network telemetry and/or other (e.g.,per gNB) data obtained via the E2 interface are used to dynamicallyadapt allocated spectrum. This data is made accessible to the xApp 418in a suitable data structure, shown in FIG. 4 as a data matrix 452,comprising data relevant to adapting allocated spectrum as describedherein.

In general, the xApp 418 requests and obtains metadata from a globalmultisite controller 120 including the threshold data, the incrementalspectrum claim change step data, and the observation time window. Basedon the metadata and the data matrix 452, the xApp 418 processes the datamatrix 452 (or other suitable data structure) of the data collected bythe RIC 416 into the actions that adapt allocated spectrum. A machinelearning (ML)/artificial intelligence (AI) and/or rules engine 454performs the data processing, including any analytics, thresholdevaluation, rule application and/or the like to make spectrum allocationdecisions. By way of a straightforward example, if the number of activeusers in a coverage area exceeds a threshold value corresponding to anamount of currently allocated spectrum, additional spectrum is allocatedvia an action decided by the engine 454. As with other implementations,the xApp 418 can proactively predict a need for additional (or reduced)spectrum in one or more of its cells, for example based on historicalmobility pattern data.

FIGS. 5 and 6 comprise a dataflow/timing diagram of communicationsbetween various components corresponding to those of FIG. 4 , in anexample CBRS implementation in which currently allocated spectrum is tobe adapted into modified allocated spectrum via the addition of CBRSspectrum. FIGS. 5 and 6 represent a state in which the need for theadditional spectrum has already been determined. The RAN/RIC includingthe xApp (block 516) communicates with the core network components(block 508) as described herein, e.g., according to specifications ofthe 3rd Generation Partnership Project (3GPP). The RAN/RIC 516 alsocommunicates with (e.g., a pool) of user devices 550 according to the3GPP Non-Access-Stratum (NAS) protocol.

To obtain the additional CBRS spectrum, the RAN/RIC 516 sends a CBSDregistration request to the global multisite controller 120, providingthe needed (standard-specified) information, e.g., including owner data,credentials, location data, and transmission characteristics. As isunderstood, this information and request is per each CBSD eNB/gNB deviceof the RAN in each location for which additional spectrum is to beallocated. Based on the request, the global multisite controller 120updates its inventory (e.g., comprising identities of base stations andassociated cells and statuses, which cells are in a particulararea/region, where they are located, which are collocated, cellbandwidth, cell frequency, and the like), and sets up telemetry. Theglobal multisite controller 120 analyzes adjacent cells and theirconfigurations to prepare an (e.g., initial) configuration correspondingto the request.

The global multisite controller 120 (which in this example communicatesdirectly with the spectrum access service (SAS) 112 via a SAS-CBSDinterface rather than through a domain proxy) forwards the CBSDregistration request to the spectrum access system 112, and receives aregistration response. In this example, the corresponding CBSD coupledto the RAN/RIC 516 is thus appropriately registered. Note that the SASevaluates requests and rejects incorrect/inappropriate requests; forpurposes of brevity and explanation, in the examples herein the CBSDrequests are not rejected, and at least some CBRS spectrum is available.

As set forth herein, to obtain a grant of CBRS spectrum, a CBSD spectruminquiry is made to the SAS 112 to determine which frequencies areavailable for the CBSD to use. The SAS responds with the frequencies;(note that the term “channel” can be used to describe a 10 MHz segmentof the CBRS spectrum).

Once the available spectrum is returned to the global multisitecontroller 120, the global multisite controller 120 selects one or moreof the frequencies based on the amount requested, e.g., corresponding tothe incremental spectrum claim step. The global multisite controller 120can request more than a single increment on behalf of the CBSD with theunderstanding that the CBSD will increase (or decrease) according to thecorresponding step size and instruct the global multisite controller 120to release any additional CBRS spectrum that is not needed, e.g., oncethe increment(s) converge to a more optimal state.

A CBSD grant request is then performed by the global multisitecontroller 120, and in this example, the response from the SAS 112grants the requested CBRS spectrum. The global multisite controller 120returns a registration response along with the spectrum grant to theRAN/RIC 516. The RAN/RIC 516 can then use the grant as appropriate,e.g., provide it to an eNB/gNB for use in transmission, according to theheartbeat requests that obtain authorization to transmit.

Once operational with the dynamic spectrum adjustments, thecommunications (below the dashed line) in FIG. 5 and in FIG. 6 canoccur. For example, the RAN/RIC 516 can obtain new state data for thexApp to modify the spectrum allocation. The RAN/RIC 516 (e.g., via thexApp) can send a monitoring and/or threshold report to the globalmultisite controller 120, which based thereon can perform analytics (ML,AI, Rules) to develop a spectrum adjustment plan, and obtainverification through SAS with respect to the spectrum adjustment plan.

In the example of FIG. 6 , to adjust the allocated CBRS spectrum, whichcan be a further increase or a decrease, the global multisite controller120 makes a new CBSD spectrum inquiry request to obtain a CBSD spectrumresponse, and based on the response, request a new spectrum grant. Whenreceived, the new spectrum grant is returned to the RAN/RIC 516 as aCBSD update with the new spectrum grant (for individual and/orcollective action enforcement to one or more cells). As is understood,further updated monitoring and/or threshold reports can be sent to theglobal multisite controller 120, with the operations and communicationsrepeated to obtain further updated spectrum grants, and so on. Also,although not explicitly shown, it is understood that the CBRS spectrumgrant can be relinquished by the RAN/RIC/xApp 516 via the globalmultisite controller 120.

Another alternative implementation is shown in FIGS. 7-9 , in which aneNB/gNB CBSD 702 performs the dynamic spectrum allocation adaption,(instead of or in addition to an xApp/RIC providing the functionalityfor any number of eNB/gNBs in the network). This single cell deploymentfacilitates local optimization. Notwithstanding, collaborativedeployment for synchronization between one or more other cells/cellgroup(s) can provide for more global optimization, e.g., withcollaborative deployment with eNB/gNB CBSD 704 in FIG. 7 can beaccomplished with a suitable extension to the X2 interface. Thisfacilitates inter-cell coordination through X2 interfaces (and/orpossibly via the domain proxy as described with reference to FIGS. 10-12) to coordinate spectrum claims collaboratively allowing global optima.

In this alternative implementation in general, the CBSD (eNB/gNB) 702includes (internal) monitoring/telemetry capabilities to measurethroughput, utilization, bearers, network slices, number of activesubscribers per cell, and so forth, as arranged in a data matrix 752 orother suitable data structure. Core network telemetry can be obtainedfrom the core via the S5 and/or N3 interfaces as additional input. Asshown in FIG. 7 , in this example implementation the CBSD 702 requeststhe metadata from the global multisite controller 120. This metadata canbe specific to the cell or cells/cell group(s).

An ML/AI/rules engine 754 monitors the data representing the actualstate versus the metadata-specified thresholds for violations accordingto the metadata's observation time window, that is, to analyze the statefor upper or lower threshold violations. In case of detecting one ormore violations, the engine 754 uses the metadata-specified incrementalspectrum claim steps to reduce or increase the allocated spectrum claimas described herein, and if appropriate enable/disable a radiotechnology or technologies. As with other implementations, the eNB/gNB702 can proactively predict a need for additional (or reduced) spectrum,for example based on historical mobility pattern data.

FIGS. 8 and 9 comprise a dataflow/timing diagram of communicationsbetween various components corresponding to those of FIG. 7 , in anexample CBRS implementation in which currently allocated spectrum is tobe adapted into modified allocated spectrum via the addition of CBRSspectrum. The communications are generally the same as in FIGS. 5 and 6and thus are not described again for purposes of brevity, except to notethat the RAN's CBSD 702 (e.g., instead of or in addition to the xApp andRIC as in FIGS. 5 and 6 ) operate to dynamically allocate spectrum asdescribed with reference to FIG. 7 . Also, although not explicitlyshown, it is understood that the CBRS spectrum grant can be relinquishedby the CBSD 702 via the global multisite controller 120.

FIGS. 10-12 show another implementation, in which a domain proxy 1014,which couples an eNB/gNB (e.g., CBSD) 1002 (and in this example aneNB/gNB (e.g., CBSD) 1004) to the spectrum access system 112 and theglobal multisite controller 120, performs the dynamic spectrumallocation adaption. This deployment facilitates optimization of a cellgroup that is coupled to the domain proxy 1014, such as in enterpriseuse cases in which more global orchestration capability that oversees asubnetwork of eNBs/gNBs is desired. For example, a retail store, acampus, a large factory and so on may have such a group of eNB/gNBs. Itis understood, however, that having a domain proxy perform dynamicspectrum allocation adaption does not preclude an eNB/gNB participate indynamic spectrum allocation adaption to an extent, such as to optimize(or recommend to the domain proxy that it desires optimization).Similarly, a RIC/xApp can participate in dynamic spectrum allocation aswell, including to limit how much CBSD spectrum the domain proxy 1014 isallowed to use, so as, for example, to try and reserve some CBSDspectrum for a nearby domain proxy (not shown) that oversees anothercell group.

In this alternative implementation in general, the domain proxy 1014includes monitoring/telemetry capabilities to measure throughput,utilization, bearers, network slices, number of active subscribers percell, and so forth, as arranged in a data matrix 1052 or other suitabledata structure. Other telemetry/monitoring data can be obtained from itsconnected eNBs/gNBs and/or the RIC/xApp 1016/1018 as additional input.As shown in FIG. 10 , in this example implementation the domain proxy1014 requests the metadata from the global multisite controller 120.

In this example, based on the metadata an ML/AI/rules engine 1054incorporated into (or otherwise coupled to) the domain proxy 1014monitors the data representing the actual state versus themetadata-specified thresholds for violations according to the metadata'sobservation time window, that is, to analyze the state for upper orlower threshold violations. In case of detecting one or more violations,the engine 1054 uses the metadata-specified incremental spectrum claimsteps to reduce or increase the allocated spectrum claim as describedherein, and if appropriate enable/disable a radio technology ortechnologies. As with other implementations, in addition to monitoring,the domain proxy 1014 can proactively predict a need for additional (orreduced) spectrum, for example based on historical mobility patterns,and thus obtain additional spectrum for use (or reduce allocatedspectrum) even without a violation.

FIGS. 11 and 12 comprise a dataflow/timing diagram of communicationsbetween various components corresponding to those of FIG. 10 , in anexample CBRS implementation in which currently allocated spectrum is tobe adapted into modified allocated spectrum via the addition of CBRSspectrum. FIGS. 11 and 12 represent a state in which the need for theadditional spectrum has already been determined. Note that communicationbetween the domain proxy 1014 and a CBSD (e.g., an eNB/gNB) may havealready taken place, e.g., the domain proxy 1014 can tell the CBSD 1016that based on the monitoring of the thresholds, the CBSD 1016 needs morespectrum and is to initiate the process by sending a CBSD registrationrequest. Similarly, the CBSD 1016 can proactively inform the domainproxy 1014 that based on its own monitoring or historical pattern data,that more spectrum is desired. The CBSD registration request in FIG. 11can thus be triggered by the CBSD 1016, or can be in response to aninvitation from the domain proxy 1014 to send the CBSD registrationrequest.

Once the domain proxy receives the CBSD registration request, the domainproxy 1014 forwards the CBSD registration request to the globalmultisite controller 120, providing the needed (standard-specified)information, e.g., including owner data, location data, and transmissioncharacteristics, e.g. based on the request from the CBSD 1016 that needsthe additional spectrum. Based on the request, the global multisitecontroller 120 updates its inventory (e.g., comprising identities ofbase stations and associated cells and statuses, which cells are in aparticular area/region, where they are located, which are collocated,cell bandwidth, cell frequency, and the like), and sets up telemetry.The global multisite controller 120 analyzes adjacent cells and theirconfigurations to prepare an (e.g., initial) configuration correspondingto the request.

The global multisite controller 120 (which in this example communicatesdirectly with the spectrum access service (SAS) 112 via a SAS-CBSDinterface rather than through the domain proxy 1014) forwards the CBSDregistration request to the spectrum access system 112, and receives aregistration response. In this example, the CBSD 1016 is thusappropriately registered. Note that the SAS evaluates requests andrejects incorrect/inappropriate requests; for purposes of brevity andexplanation, in the examples herein the CBSD requests are not rejected,and at least some CBRS spectrum is available.

However the registration response is not yet returned by the spectrumaccess service (SAS) 112 to the domain proxy 1014. Instead, the responsewill be returned when a grant of CBRS spectrum is obtained by the SAS112.

As set forth herein, to obtain a grant of CBRS spectrum, a CBSD spectruminquiry is made by the global multisite controller 120 to the SAS 112 todetermine which frequencies are available for the domain proxy 1014 (andultimately the CBSD 1016) to use. The SAS responds with the frequencies;(note that the term “channel” can be used to describe a 10 MHz segmentof the CBRS spectrum).

Once the available spectrum is returned to the global multisitecontroller 120, the global multisite controller 120 selects one or moreof the frequencies based on the amount requested, e.g., corresponding tothe incremental spectrum claim step and the initial configuration plan.The global multisite controller 120 can request more than a singleincrement on behalf of the CBSD with the understanding that the CBSDwill increase (or decrease) according to the corresponding step size andinstruct the global multisite controller 120 to release any additionalCBRS spectrum that is not needed, e.g., once the increment(s) convergeto a more optimal state.

A CBSD grant request is then sent by the global multisite controller120, and in this example, the response from the SAS 112 grants therequested CBRS spectrum. The global multisite controller 120 returns aregistration response along with the spectrum grant to the domain proxy1014, which in turn returns the registration response to the CBSD 1016.Note that in the example of FIGS. 12 and 12 the CBSD 1016 is configuredto expect such a combined response to a CBSD registration request,however it is feasible for a domain proxy to interact with a CBSD withindividual CBSD requests/responses, without the CBSD necessarily knowingof the global multisite controller's involvement.

Once the spectrum is granted, the CBSD 1016 (via heartbeat-basedauthorizations) can schedule its CBRS-capable user equipment devices (ofdevice pool 1050) to transmit and receive in the granted CBRS spectrum.The CBSD and domain proxy can exchange various push-and-pull metrics(e.g., obtained via performance monitoring) for the observation timewindow.

Consider that in the example of FIGS. 11 and 12 that the currentlyallocated CBRS spectrum (via the communications above the dashed line inFIG. 11 ) is to be adapted into a modified amount of spectrum (via thecommunications below the dashed line in FIG. 11 , and in FIG. 12 ). Amonitoring and/or threshold report, which can be for a group of CBSDs,is sent to the global multisite controller 120.

The global multisite controller 120 can perform analytics (ML, AI,Rules) on the monitoring and/or threshold report to develop a spectrumadjustment plan, and obtain verification through SAS with respect to thespectrum adjustment plan. In the example of FIG. 12 , to adjust theallocated CBRS spectrum, which can be a further increase or a decrease,the global multisite controller 120 makes a new CBSD spectrum inquiryrequest to obtain a CBSD spectrum response, and based on the response,request a new spectrum grant. When received, the new spectrum grant isreturned to the domain proxy 1014 as a CBSD update with the new spectrumgrant (for individual and/or collective action enforcement to one ormore cells), which in turn is returned by the domain proxy 1014 to theCBSD 1016. As is understood, further updated monitoring and/or thresholdreports can be sent to the global multisite controller 120, with theoperations and communications repeated to obtain further updatedspectrum grants, and so on. Also, although not explicitly shown, it isunderstood that the CBRS spectrum grant can be relinquished by the CBSD1016/the domain proxy 1014 via the global multisite controller 120.

Another example implementation is shown in FIGS. 13-15 in whichclient-side spectrum as a service that facilitates adapting/dynamicallyallocating spectrum is incorporated into a device 1360. Client-sidespectrum as a service can be independent, or can be in addition tonetwork-based spectrum as a service as represented in FIGS. 1-12 .Spectrum control can be a per-customer solution, or per-enterprisesolution (e.g., configured on a company's laptops).

Note that while FIG. 13 shows a new radio (e.g., 5G) example with anxApp 1318/RIC 1316, other client-side spectrum as a serviceimplementations (e.g., LTE) are feasible. In general, as the various 5Gnetwork components have been previously described with reference to FIG.4 , these components are not described again for purposes of brevity.Further, 6G is about to be standardized and is expected to be applicableto the technology described herein as well, in which the THz spectrumcan be integrated into an as-a-Service offering.

As shown in FIG. 13 , the device 1360, which comprises applicationprograms 1382, an operating system 1384 and hardware 1386, is configuredto implement spectrum as a service, which enables the device 1360 tosignal desired bandwidth requirements into the network. In onealterative, a spectrum as a service application program 1368 detects theneed for additional or reduced bandwidth, and operates to signal thedesired bandwidth requirements to the network. In another alternative,an embedded controller, e.g., integrated into firmware (block 1370) oroperating system extension can adapt the device 1360 to obtain thedesired bandwidth. As is understood, a combination of an applicationprogram, operating system extension and/or an embedded controller can beimplemented to perform the device-based bandwidth management operations.

In one implementation, the desired bandwidth requirements can correspondto connectivity metadata. Such connectivity metadata can be gatheredfrom running/active application programs 1362 on a user device such asthe device 1360, the operating system 1364 and/or network buffer statusinformation and the like. Sending connectivity metadata to a networkdevice, e.g., the global multisite controller 120 in FIG. 13 , resultsin receiving scheduling uplink/downlink communications via spectrumcorresponding to amount of bandwidth. For example the global multisitecontroller 120 can operate to transform the connectivity metadata into asuitable spectrum and assess an amount, representative of an amount ofbandwidth to be requested, for use in scheduling the user equipment.

In any event, the operating system and/or application can securelyinteract with the network infrastructure to request spectrum on demandas a service. Control-points on the device can be used as a secureanchor point on the device for decision making and control-planesignaling.

The spectrum request can be based on telemetry data known to the device,can be event driven (a certain application has started), can be based ona notification (e.g., of virtual reality or a high definition video)and/or heuristics and the like.

By way of example, one feasible action the device can perform is toincrease bandwidth before and/or during a video call, which results inhigher quality viewing experience. Other high-bandwidth usage cases maysimilarly benefit from receiving additional bandwidth from the network.After the video call terminates, the device acts to reduce bandwidth,which can result in a reduced bill, and less consumption of deviceenergy state. Another such action is to configure best effort servicewhen a user is interacting with an email program.

Performance versus battery life can be balanced, such as to only turn onadaptive spectrum operations when needed, else drain the battery (viamore processing), increase operational cost and so on. The adaptivespectrum operations can be based on an iterative algorithm, such as tostart with high bandwidth claim then reduce incrementally, orvice-versa. Reinforcement learning can facilitate automated actions, soas to be self-adjusting per use case.

Spectrum as a service to manage bandwidth can be triggered reactivelyduring service invocation/termination, as in the above video-callexample. Bandwidth can be increased or decreased proactively based onhistorical data, e.g., user patterns, behavior of other devices/userprofiles for a given location, time, a mix of application programsactive and/or installed on the device (which can be identified). As withother implementations, the UL:DL ratio and number of carrieraggregations used can be adjusted based on a usage scenario.

FIGS. 14 and 15 comprise a dataflow/timing diagram of communicationsbetween various components corresponding to those of FIG. 13 , in anexample CBRS implementation in which currently allocated spectrum is tobe adapted into modified allocated spectrum via the addition of CBRSspectrum. In this example, the device 1360 works with a RAN/RIC that hasan xApp (block 1516) that performs the CBSD-related operations todynamically allocate CBRS spectrum for the device 1360 via the globalmultisite controller 120, including based on data provided from thedevice to the global multisite controller 120.

FIGS. 14 and 15 represent a state in which a need for CBRS spectrum hasalready been determined. The initial provisioning operations (above thedashed line in FIG. 15 ) are the same as described with reference toFIG. 4 , and thus are not described again for purposes of brevity. Inthis example, via the global multisite controller 120 and SAS 112communications, CBRS spectrum is granted to the RAN/RIC/xApp representedby block 1516.

Turning to operation with dynamic spectrum adjustments, (as shown belowthe dashed line in FIG. 15 and in FIG. 16 ), as set forth herein, thedevice 1360 is configured to provide data to the global multisitecontroller 120, which can include push and pull metrics,application-related data and/or session setup/modification information.The RAN/RIC/xApp 1516 can send a monitoring and/or threshold report tothe global multisite controller 120, as can the core 1408. Based on thedevice data, the xApp data and/or the core data, the global multisitecontroller 120 can perform analytics (ML, AI, Rules) to develop aspectrum adjustment plan, and obtain verification through the SAS 112with respect to the spectrum adjustment plan.

In the example of FIG. 15 , to adjust the allocated CBRS spectrum, whichcan be a further increase or a decrease, the global multisite controller120 makes a new CBSD spectrum inquiry request to obtain a CBSD spectrumresponse, and based on the response, requests a new spectrum grant. Whenreceived, the new spectrum grant is returned to the RAN/RIC 1416 as aCBSD update with the new spectrum grant (for individual and/orcollective action enforcement to one or more cells). RAN reselection ofa mobility request, and/or quality of service (QoS) reconfigurationinformation can be returned to the core 1408. Access network changes,network (re)-selection, QoS/bearer modifications and the like can bereturned by the global multisite controller 120 to the device 1360.

As is understood, the data sent (below the dashed line in FIG. 14 ) tothe global multisite controller 120 can be re-sent, with similarresponses returned, and so on. Also, although not explicitly shown, itis understood that the CBRS spectrum grant can be relinquished by theRAN/RIC/xApp 1416 via the global multisite controller 120.

FIGS. 16A and 16B show additional examples of dynamic spectrumallocation to adapt to current state data and/or to proactively controlthe amount of allocated spectrum, as well as hotspot location. FIG. 16Ais directed to a single cell scenario with hotspot relocation withinthat single cell, while FIG. 16B is directed to a multiple cell scenariowith hotspot movement across cell boundaries.

Consider that in FIG. 16A a cell in a first state, labeled 1670(1), has20 MHz of spectrum (or additional, e.g., CBRS spectrum) allocatedthereto. The cell (in the first state) 1670(1) has a relocatable hotspotas represented by the shaded circle therein; note that the term“hotspot” is not intended to be limited to any particular frequency,e.g., the hotspot can be, but is not necessarily a Wi-Fi hotspot, andindeed can be based on CBRS spectrum. As set forth herein, relocation ofa hotspot can be done in various ways, e.g., the hotspot can be mobile,a hotspot can be activated in a (mostly) stationary or fixed devicelocation and deactivated in view of a different activated device in adifferent location, and so on. As shown in FIG. 16A, the cell in asecond state 1670(2) has increased its spectrum (shown as 100 MHz) asdescribed herein, and further, has relocated and increased the size ofits hotspot.

In FIG. 16B three cells are in a first state as represented by cellslabeled 1680(1), 1682(1) and 1684(1), having allocated spectrum of 10MHz, 100 MHz and 20 MHz, respectively. In a second state followingdynamic spectrum allocation, the three cells labeled 1680(2), 1682(2)and 1684(3) have reallocated spectrum of 10 MHz (unchanged), 10 MHz(reduced) and 110 MHz (increased), respectively. Further, the hotspothas relocated from the cell labeled 1682(1) to the cell labeled 1684(2).

One or more aspects can be embodied in a system, such as represented inFIG. 17 , and for example can comprise a memory that stores computerexecutable components and/or operations, and a processor that executescomputer executable components and/or operations stored in the memory(e.g., of a user device). Example operations can comprise operation1702, which represents determining connectivity metadata, representativeof requested bandwidth, based on a selection criterion. Operation 1704represents sending the connectivity metadata to a network device fortransformation into spectrum corresponding to an amount of bandwidth.Operation 1706 represents receiving scheduling data for communicatingvia the spectrum.

Further operations can comprise determining ratio data, representativeof a downlink-to-uplink ratio to be requested, based on a usagecriterion, and signaling the ratio data to the communications system.

Determining the connectivity metadata based on the selection criterioncan comprise establishing or setting up a video communication.

Determining the connectivity metadata based on the selection criterioncan comprise evaluating performance data during a video communication.

Determining the connectivity metadata based on the selection criterioncan comprise ending a video communication.

Determining the connectivity metadata based on the selection criterioncan comprise evaluating historical data for proactively signaling theconnectivity metadata to a communications system. Evaluating thehistorical data can comprise evaluating at least one of: device usagepattern data, other device behavior data, or other user profile dataother than a current user profile currently associated with the userdevice.

Determining the connectivity metadata based on the selection criterioncan comprise evaluating an execution of an application program installedon the user device.

Further operations can comprise sending at least one of: metrics data,application data or session information to a system controller thatoperates to determine spectrum allocation.

A spectrum-as-a-service application program executing via the userdevice can perform the determining the bandwidth data.

The user device can comprise a spectrum-as-a-service program integratedinto a device operating system.

Sending the connectivity metadata to a network device can comprisecommunicating with a system controller that returns a spectrum grantapplicable to a network device associated with a coverage area in whichthe user device is communicating.

The spectrum grant can be a portion of citizens broadband radio servicespectrum on which the user device is scheduled for furthercommunications.

One or more aspects can be embodied in a system, such as represented inFIG. 18 , and for example can comprise a memory that stores computerexecutable components and/or operations, and a processor that executescomputer executable components and/or operations stored in the memory.Example operations can comprise operation 1802, which representscommunicating with a network device to request an increase in userdevice bandwidth over a current bandwidth. Operation 1804 represents, inresponse to the request, obtaining additional bandwidth over the currentbandwidth resulting in an updated bandwidth for the user device.

The additional bandwidth can correspond to the user device beingscheduled for communications on citizens broadband radio servicespectrum. Further operations can comprise communicating with the networkdevice to request a decrease in user device bandwidth below the updatedbandwidth, and in response to the request, obtaining reduced bandwidthbelow the updated bandwidth resulting in a further updated bandwidth forthe user device.

Further operations can comprise determining a downlink-to-uplink ratioto be requested based on a user device usage criterion, and signalingthe desired downlink-to-uplink ratio to the communications system.

FIG. 19 summarizes various example operations, e.g., corresponding to amachine-readable storage medium, comprising executable instructionsthat, when executed by a processor, facilitate performance ofoperations. Operation 1902 represents determining, based on a usagecriterion applicable to the user device, an amount of additionalbandwidth to request. Operation 1904 represents communicatinginformation indicating the amount of additional bandwidth to request toa network device. Operation 1906 represents receiving scheduling datathat is to facilitate further communication of spectrum that is toenable the additional bandwidth.

Further operations can comprise requesting a modified downlink-to-uplinkratio from a current downlink-to-uplink ratio based on the usagecriterion.

Determining, based on the usage criterion, the amount of additionalbandwidth can comprise analyzing at least one of: a video call, anamount of uplink data to send, an amount of downlink data to receive, orhistorical data corresponding to bandwidth determinations based on theusage criterion.

As can be seen, the technology described herein increases spectralefficiency in wireless networks, including private wireless networks,and operates as a strategic control point for private wirelessdeployment of any scale including small, medium or large deployments.The technology described herein is applicable to licensed, unlicensedand shared types of spectrum. The technology described herein can beimplemented as a spectrum as a service (SaaS) model, which can be usedfor “pay-as-you-go” spectrum allocation. The technology described hereinimproves a customer experience and quality of service, for example whencompared to best effort deployments.

Turning to aspects in general, a wireless communication system canemploy various cellular systems, technologies, and modulation schemes tofacilitate wireless radio communications between devices (e.g., a UE andthe network equipment). While example embodiments might be described for5G new radio (NR) systems, the embodiments can be applicable to anyradio access technology (RAT) or multi-RAT system where the UE operatesusing multiple carriers e.g. LTE FDD/TDD, GSM/GERAN, CDMA2000 etc. Forexample, the system can operate in accordance with global system formobile communications (GSM), universal mobile telecommunications service(UMTS), long term evolution (LTE), LTE frequency division duplexing (LTEFDD, LTE time division duplexing (TDD), high speed packet access (HSPA),code division multiple access (CDMA), wideband CDMA (WCMDA), CDMA2000,time division multiple access (TDMA), frequency division multiple access(FDMA), multi-carrier code division multiple access (MC-CDMA),single-carrier code division multiple access (SC-CDMA), single-carrierFDMA (SC-FDMA), orthogonal frequency division multiplexing (OFDM),discrete Fourier transform spread OFDM (DFT-spread OFDM) single carrierFDMA (SC-FDMA), Filter bank based multi-carrier (FBMC), zero tailDFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency divisionmultiplexing (GFDM), fixed mobile convergence (FMC), universal fixedmobile convergence (UFMC), unique word OFDM (UW-OFDM), unique wordDFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM,resource-block-filtered OFDM, Wi Fi, WLAN, WiMax, and the like. However,various features and functionalities of system are particularlydescribed wherein the devices (e.g., the UEs and the network equipment)of the system are configured to communicate wireless signals using oneor more multi carrier modulation schemes, wherein data symbols can betransmitted simultaneously over multiple frequency subcarriers (e.g.,OFDM, CP-OFDM, DFT-spread OFDM, UFMC, FMBC, etc.). The embodiments areapplicable to single carrier as well as to multicarrier (MC) or carrieraggregation (CA) operation of the UE. The term carrier aggregation (CA)is also called (e.g. interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi-carrier operation”, “multi-carrier”transmission and/or reception. Note that some embodiments are alsoapplicable for Multi RAB (radio bearers) on some carriers (that is dataplus speech is simultaneously scheduled).

In various embodiments, the system can be configured to provide andemploy 5G wireless networking features and functionalities. With 5Gnetworks that may use waveforms that split the bandwidth into severalsub-bands, different types of services can be accommodated in differentsub-bands with the most suitable waveform and numerology, leading toimproved spectrum utilization for 5G networks. Notwithstanding, in themmWave spectrum, the millimeter waves have shorter wavelengths relativeto other communications waves, whereby mmWave signals can experiencesevere path loss, penetration loss, and fading. However, the shorterwavelength at mmWave frequencies also allows more antennas to be packedin the same physical dimension, which allows for large-scale spatialmultiplexing and highly directional beamforming.

Performance can be improved if both the transmitter and the receiver areequipped with multiple antennas. Multi-antenna techniques cansignificantly increase the data rates and reliability of a wirelesscommunication system. The use of multiple input multiple output (MIMO)techniques, which was introduced in the third-generation partnershipproject (3GPP) and has been in use (including with LTE), is amulti-antenna technique that can improve the spectral efficiency oftransmissions, thereby significantly boosting the overall data carryingwireless capacity of wireless systems. The use of multiple-inputmultiple-output (MIMO) techniques can improve mmWave communications;MIMO can be used for achieving diversity gain, spatial multiplexing gainand beamforming gain. Carrier-aggregation techniques are considered aswell to license assisted access as a means to combine multiple radiotypes such as cellular and WiFi.

Note that using multi-antennas does not always mean that MIMO is beingused. For example, a configuration can have two downlink antennas, andthese two antennas can be used in various ways. In addition to using theantennas in a 2×2 MIMO scheme, the two antennas can also be used in adiversity configuration rather than MIMO configuration. Even withmultiple antennas, a particular scheme might only use one of theantennas (e.g., LTE specification's transmission mode 1, which uses asingle transmission antenna and a single receive antenna). Or, only oneantenna can be used, with various different multiplexing, precodingmethods etc.

The MIMO technique uses a commonly known notation (M×N) to representMIMO configuration in terms number of transmit (M) and receive antennas(N) on one end of the transmission system. The common MIMOconfigurations used for various technologies are: (2×1), (1×2), (2×2),(4×2), (8×2) and (2×4), (4×4), (8×4). The configurations represented by(2×1) and (1×2) are special cases of MIMO known as transmit diversity(or spatial diversity) and receive diversity. In addition to transmitdiversity (or spatial diversity) and receive diversity, other techniquessuch as spatial multiplexing (comprising both open-loop andclosed-loop), beamforming, and codebook-based precoding can also be usedto address issues such as efficiency, interference, and range.

Referring now to FIG. 20 , illustrated is a schematic block diagram ofan example end-user device (such as user equipment) that can be a mobiledevice 2000 capable of connecting to a network in accordance with someembodiments described herein. Although a mobile handset 2000 isillustrated herein, it will be understood that other devices can be amobile device, and that the mobile handset 2000 is merely illustrated toprovide context for the embodiments of the various embodiments describedherein. The following discussion is intended to provide a brief, generaldescription of an example of a suitable environment 2000 in which thevarious embodiments can be implemented. While the description includes ageneral context of computer-executable instructions embodied on amachine-readable storage medium, those skilled in the art will recognizethat the various embodiments also can be implemented in combination withother program modules and/or as a combination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can include computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM,digital video disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The handset 2000 includes a processor 2002 for controlling andprocessing all onboard operations and functions. A memory 2004interfaces to the processor 2002 for storage of data and one or moreapplications 2006 (e.g., a video player software, user feedbackcomponent software, etc.). Other applications can include voicerecognition of predetermined voice commands that facilitate initiationof the user feedback signals. The applications 2006 can be stored in thememory 2004 and/or in a firmware 2008, and executed by the processor2002 from either or both the memory 2004 or/and the firmware 2008. Thefirmware 2008 can also store startup code for execution in initializingthe handset 2000. A communications component 2010 interfaces to theprocessor 2002 to facilitate wired/wireless communication with externalsystems, e.g., cellular networks, VoIP networks, and so on. Here, thecommunications component 2010 can also include a suitable cellulartransceiver 2011 (e.g., a GSM transceiver) and/or an unlicensedtransceiver 2013 (e.g., Wi-Fi, WiMax) for corresponding signalcommunications. The handset 2000 can be a device such as a cellulartelephone, a PDA with mobile communications capabilities, andmessaging-centric devices. The communications component 2010 alsofacilitates communications reception from terrestrial radio networks(e.g., broadcast), digital satellite radio networks, and Internet-basedradio services networks.

The handset 2000 includes a display 2012 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 2012 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 2012 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface2014 is provided in communication with the processor 2002 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE2094) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 2000, for example. Audio capabilities areprovided with an audio I/O component 2016, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 2016 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 2000 can include a slot interface 2018 for accommodating aSIC (Subscriber Identity Component) in the form factor of a cardSubscriber Identity Module (SIM) or universal SIM 2020, and interfacingthe SIM card 2020 with the processor 2002. However, it is to beappreciated that the SIM card 2020 can be manufactured into the handset2000, and updated by downloading data and software.

The handset 2000 can process IP data traffic through the communicationcomponent 2010 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, a gateway or other forms of aggregation points, etc.,through an ISP or broadband cable provider. Thus, VoIP traffic can beutilized by the handset 800 and IP-based multimedia content can bereceived in either an encoded or decoded format.

A video processing component 2022 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 2022can aid in facilitating the generation, editing and sharing of videoquotes. The handset 2000 also includes a power source 2024 in the formof batteries and/or an AC power subsystem, which power source 2024 caninterface to an external power system or charging equipment (not shown)by a power I/O component 2026.

The handset 2000 can also include a video component 2030 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 2030 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 2032 facilitates geographically locating the handset 2000. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 2034facilitates the user initiating the quality feedback signal. The userinput component 2034 can also facilitate the generation, editing andsharing of video quotes. The user input component 2034 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 2006, a hysteresis component 2036facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 2038 can be provided that facilitatestriggering of the hysteresis component 2038 when the Wi-Fi transceiver2013 detects the beacon of the access point. A SIP client 2040 enablesthe handset 2000 to support SIP protocols and register the subscriberwith the SIP registrar server. The applications 2006 can also include aclient 2042 that provides at least the capability of discovery, play andstore of multimedia content, for example, music.

The handset 2000, as indicated above related to the communicationscomponent 810, includes an indoor network radio transceiver 2013 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode GSM handset 2000. The handset 2000 canaccommodate at least satellite radio services through a handset that cancombine wireless voice and digital radio chipsets into a single handhelddevice.

In order to provide additional context for various embodiments describedherein, FIG. 21 and the following discussion are intended to provide abrief, general description of a suitable computing environment 2100 inwhich the various embodiments of the embodiment described herein can beimplemented. While the embodiments have been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that theembodiments can be also implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the various methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, Internet of Things (IoT)devices, distributed computing systems, as well as personal computers,hand-held computing devices, microprocessor-based or programmableconsumer electronics, and the like, each of which can be operativelycoupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray disc (BD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, solid state drives or other solid statestorage devices, or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 21 , the example environment 2100 forimplementing various embodiments of the aspects described hereinincludes a computer 2102, the computer 2102 including a processing unit2104, a system memory 2106 and a system bus 2108. The system bus 2108couples system components including, but not limited to, the systemmemory 2106 to the processing unit 2104. The processing unit 2104 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 2104.

The system bus 2108 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 2106includes ROM 2110 and RAM 2112. A basic input/output system (BIOS) canbe stored in a non-volatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer2102, such as during startup. The RAM 2112 can also include a high-speedRAM such as static RAM for caching data.

The computer 2102 further includes an internal hard disk drive (HDD)2114 (e.g., EIDE, SATA), one or more external storage devices 2116(e.g., a magnetic floppy disk drive (FDD) 2116, a memory stick or flashdrive reader, a memory card reader, etc.) and an optical disk drive 2120(e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.).While the internal HDD 2114 is illustrated as located within thecomputer 2102, the internal HDD 2114 can also be configured for externaluse in a suitable chassis (not shown). Additionally, while not shown inenvironment 2100, a solid state drive (SSD), non-volatile memory andother storage technology could be used in addition to, or in place of,an HDD 2114, and can be internal or external. The HDD 2114, externalstorage device(s) 2116 and optical disk drive 2120 can be connected tothe system bus 2108 by an HDD interface 2124, an external storageinterface 2126 and an optical drive interface 2128, respectively. Theinterface 2124 for external drive implementations can include at leastone or both of Universal Serial Bus (USB) and Institute of Electricaland Electronics Engineers (IEEE) 2094 interface technologies. Otherexternal drive connection technologies are within contemplation of theembodiments described herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 2102, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, it should beappreciated by those skilled in the art that other types of storagemedia which are readable by a computer, whether presently existing ordeveloped in the future, could also be used in the example operatingenvironment, and further, that any such storage media can containcomputer-executable instructions for performing the methods describedherein.

A number of program modules can be stored in the drives and RAM 2112,including an operating system 2130, one or more application programs2132, other program modules 2134 and program data 2136. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 2112. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 2102 can optionally include emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 2130, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 21 . In such an embodiment, operating system 2130 can include onevirtual machine (VM) of multiple VMs hosted at computer 2102.Furthermore, operating system 2130 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplications 2132. Runtime environments are consistent executionenvironments that allow applications 2132 to run on any operating systemthat includes the runtime environment. Similarly, operating system 2130can support containers, and applications 2132 can be in the form ofcontainers, which are lightweight, standalone, executable packages ofsoftware that include, e.g., code, runtime, system tools, systemlibraries and settings for an application.

Further, computer 2102 can be enabled with a security module, such as atrusted processing module (TPM). For instance with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 2102, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 2102 throughone or more wired/wireless input devices, e.g., a keyboard 2138, a touchscreen 2140, and a pointing device, such as a mouse 2142. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 2104 through an input deviceinterface 2144 that can be coupled to the system bus 2108, but can beconnected by other interfaces, such as a parallel port, an IEEE 2094serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 2146 or other type of display device can be also connected tothe system bus 2108 via an interface, such as a video adapter 2148. Inaddition to the monitor 2146, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 2102 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 2150. The remotecomputer(s) 2150 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer2102, although, for purposes of brevity, only a memory/storage device2152 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 2154 and/orlarger networks, e.g., a wide area network (WAN) 2156. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 2102 can beconnected to the local network 2154 through a wired and/or wirelesscommunication network interface or adapter 2158. The adapter 2158 canfacilitate wired or wireless communication to the LAN 2154, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 2158 in a wireless mode.

When used in a WAN networking environment, the computer 2102 can includea modem 2160 or can be connected to a communications server on the WAN2156 via other means for establishing communications over the WAN 2156,such as by way of the Internet. The modem 2160, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 2108 via the input device interface 2144. In a networkedenvironment, program modules depicted relative to the computer 2102 orportions thereof, can be stored in the remote memory/storage device2152. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

When used in either a LAN or WAN networking environment, the computer2102 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 2116 asdescribed above. Generally, a connection between the computer 2102 and acloud storage system can be established over a LAN 2154 or WAN 2156e.g., by the adapter 2158 or modem 2160, respectively. Upon connectingthe computer 2102 to an associated cloud storage system, the externalstorage interface 2126 can, with the aid of the adapter 2158 and/ormodem 2160, manage storage provided by the cloud storage system as itwould other types of external storage. For instance, the externalstorage interface 2126 can be configured to provide access to cloudstorage sources as if those sources were physically connected to thecomputer 2102.

The computer 2102 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11(a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 8 GHz radio bands, at an 21Mbps (802.11b) or 84 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10BaseT” wiredEthernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor also can be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” “queue”, and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan include various types of media that are readable by a computer, suchas hard-disc drives, zip drives, magnetic cassettes, flash memory cardsor other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to include, without beinglimited, these and any other suitable types of memory.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated example aspects of the embodiments. In thisregard, it will also be recognized that the embodiments include a systemas well as a computer-readable medium having computer-executableinstructions for performing the acts and/or events of the variousmethods.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, solid state drive (SSD) or other solid-state storagetechnology, compact disk read only memory (CD ROM), digital versatiledisk (DVD), Blu-ray disc or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices or other tangible and/or non-transitory media which canbe used to store desired information.

In this regard, the terms “tangible” or “non-transitory” herein asapplied to storage, memory or computer-readable media, are to beunderstood to exclude only propagating transitory signals per se asmodifiers and do not relinquish rights to all standard storage, memoryor computer-readable media that are not only propagating transitorysignals per se. Computer-readable storage media can be accessed by oneor more local or remote computing devices, e.g., via access requests,queries or other data retrieval protocols, for a variety of operationswith respect to the information stored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and includes any information delivery or transport media. Theterm “modulated data signal” or signals refers to a signal that has oneor more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communications media include wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media

Further, terms like “user equipment,” “user device,” “mobile device,”“mobile,” station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication network or service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Likewise, the terms “access point,” “node B,” “base station,”“evolved Node B,” “cell,” “cell site,” and the like, can be utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Data and signalingstreams can be packetized or frame-based flows. It is noted that in thesubject specification and drawings, context or explicit distinctionprovides differentiation with respect to access points or base stationsthat serve and receive data from a mobile device in an outdoorenvironment, and access points or base stations that operate in aconfined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a wireless capacity to make inferencebased on complex mathematical formalisms) which can provide simulatedvision, sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the subjectapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes” and “including” andvariants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

The above descriptions of various embodiments of the subject disclosureand corresponding figures and what is described in the Abstract, aredescribed herein for illustrative purposes, and are not intended to beexhaustive or to limit the disclosed embodiments to the precise formsdisclosed. It is to be understood that one of ordinary skill in the artmay recognize that other embodiments having modifications, permutations,combinations, and additions can be implemented for performing the same,similar, alternative, or substitute functions of the disclosed subjectmatter, and are therefore considered within the scope of thisdisclosure. Therefore, the disclosed subject matter should not belimited to any single embodiment described herein, but rather should beconstrued in breadth and scope in accordance with the claims below.

What is claimed is:
 1. A user device, comprising: a processor; and amemory that stores executable instructions that, when executed by theprocessor, facilitate performance of operations, the operationscomprising: determining connectivity metadata, representative ofrequested bandwidth, based on a selection criterion; sending theconnectivity metadata to a network device for transformation intospectrum corresponding to an amount of bandwidth; and receivingscheduling data for communicating via the spectrum.
 2. The user deviceof claim 1, wherein the operations further comprise determining ratiodata, representative of a downlink-to-uplink ratio to be requested,based on a usage criterion, and signaling the ratio data to thecommunications system.
 3. The user device of claim 1, wherein thedetermining the connectivity metadata based on the selection criterioncomprises establishing or setting up a video communication.
 4. The userdevice of claim 1, wherein the determining the connectivity metadatabased on the selection criterion comprises evaluating performance dataduring a video communication.
 5. The user device of claim 1, wherein thedetermining the connectivity metadata based on the selection criterioncomprises ending a video communication.
 6. The user device of claim 1,wherein the determining the connectivity metadata based on the selectioncriterion comprises evaluating historical data for proactively signalingthe bandwidth data to a communications system.
 7. The user device ofclaim 6, wherein the evaluating the historical data comprises evaluatingat least one of: device usage pattern data, other device behavior data,or other user profile data other than a current user profile currentlyassociated with the user device.
 8. The user device of claim 1, whereinthe determining the connectivity metadata based on the selectioncriterion comprises evaluating an execution of an application programinstalled on the user device.
 9. The user device of claim 1, wherein theoperations further comprise sending at least one of: metrics data,application data or session information to a system controller thatoperates to determine spectrum allocation.
 10. The user device of claim1, wherein a spectrum-as-a-service application program executing via theuser device performs the determining the bandwidth data.
 11. The userdevice of claim 1, wherein the user device comprises aspectrum-as-a-service program integrated into a device operating system.12. The user device of claim 1, wherein the sending the connectivitymetadata to a network device comprises communicating with a systemcontroller that returns a spectrum grant applicable to a network deviceassociated with a coverage area in which the user device iscommunicating.
 13. The user device of claim 1, wherein the spectrumgrant is a portion of citizens broadband radio service spectrum on whichthe user device is scheduled for further communications.
 14. A userdevice, comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, the operations comprising: communicating witha network device to request an increase in user device bandwidth over acurrent bandwidth; and in response to the request, obtaining additionalbandwidth over the current bandwidth resulting in an updated bandwidthfor the user device.
 15. The user device of claim 14, wherein theadditional bandwidth corresponds to the user device being scheduled forcommunications on citizens broadband radio service spectrum.
 16. Theuser device of claim 14, wherein the operations further comprisecommunicating with the network device to request a decrease in userdevice bandwidth below the updated bandwidth, and in response to therequest, obtaining reduced bandwidth below the updated bandwidthresulting in a further updated bandwidth for the user device.
 17. Theuser device of claim 14, wherein the operations further comprisedetermining a downlink-to-uplink ratio to be requested based on a userdevice usage criterion, and signaling the desired downlink-to-uplinkratio to the communications system.
 18. A non-transitorymachine-readable medium, comprising executable instructions that, whenexecuted by a processor of a user device, facilitate performance ofoperations, the operations comprising: determining, based on a usagecriterion applicable to the user device, an amount of additionalbandwidth to request; communicating information indicating the amount ofadditional bandwidth to request to a network device; and receivingscheduling data that is to facilitate further communication of spectrumthat is to enable the additional bandwidth.
 19. The non-transitorymachine-readable medium of claim 18, wherein the operations furthercomprise requesting a modified downlink-to-uplink ratio from a currentdownlink-to-uplink ratio based on the usage criterion.
 20. Thenon-transitory machine-readable medium of claim 18, wherein thedetermining, based on the usage criterion, the amount of additionalbandwidth comprises analyzing at least one of: a video call, an amountof uplink data to send, an amount of downlink data to receive, orhistorical data corresponding to bandwidth determinations based on theusage criterion.